Systems and methods for performing load optimization of medications in an electronic medication storage cabinet

ABSTRACT

An electronic medication storage cabinet includes a plurality of drawers configured with a plurality of sensors arranged to identify a positioning of storage pockets within the drawers. Upon receiving an indication of a new medicine container to be loaded in the cabinet, a sequence of steps to load the medicine container into the cabinet is generated based on a mapping algorithm. A first step is displayed on a display the cabinet, and a determination is made as to whether the first step is associated with one of the plurality of drawers. In response to determining that the first step is associated with one of the plurality of drawers, the drawer is automatically unlocked. In response to determining that the first step is successfully completed, a determination of whether execution of any additional steps is pending and indicated on the display.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit as a nonprovisional of U.S.Provisional Application Ser. No. 62/865,048, entitled “SYSTEMS ANDMETHODS FOR PERFORMING LOAD OPTIMIZATION OF MEDICATIONS IN AN ELECTRONICMEDICATION STORAGE CABINET,” filed on Jun. 21, 2019, the entirety ofwhich is incorporated herein by reference.

TECHNICAL FIELD

This application relates generally to optimizing space within a device,such as an electronic medication storage cabinets used in healthcareorganizations.

BACKGROUND

Medication dispensing cabinets are frequently utilized in hospitals toserve multiple patients. Prescription medication may be placed in suchdispensing cabinets. Periodically the medications stored in the cabinetmay be updated to assure that medications commonly prescribed byphysicians are available as prescribing patterns often change over time.When this occurs medication are removed from the dispensing cabinets tomake room for other medications. However, it is often difficult to gaugehow much space a particular medication will require, as well as how muchspace is available in the medication dispensing cabinets. With differingsizes of medications, drawers, and storage compartments within thedrawers, it becomes time consuming to organize items to create adequatestorage space.

Pharmacists, nurses, and other operators of the dispensing cabinetsoften struggle to place critical medications in cabinets that are closeto full capacity. Thus, with the ever-growing need for quick, efficient,and reliable access to medication for patients, the need to efficientlyplace and locate medication has increased. Methods of optimizingavailable storage space for patient medication are desired.

SUMMARY

Typically, a user, such as a pharmacy technician, when placing orloading new medications into to an electronic medication storage unit,such as an automated medication dispensing cabinet, reconfigures theelectronic medication storage unit. However, the user, at the time ofloading the medications into the electronic medication storage unit doesnot have the necessary tools to optimize the contents of the electronicmedication storage unit.

Accordingly, there is a need for methods and systems that can optimizethe space of an electronic medication storage unit having predefinedstorage capabilities and requirements, and to guide a user through thesteps to optimally load the medication into the electronic medicationstorage unit. Disclosed implementations are able to efficiently provideoptimization instructions for use in a healthcare organization.

In accordance with some implementations, a method includes providing anelectronic medication storage unit comprising a plurality of drawers,each drawer configured with a plurality of storage pockets, the drawerconfigured with a plurality of sensors arranged to identify apositioning of the plurality of storage pockets within the drawer. Themethod includes receiving an indication of a new medicine container tobe loaded in the electronic medication storage unit. The method includesdisplaying a first step of a sequence of one or more steps to load themedicine container into an electronic medication storage cabinet on adisplay on the electronic medication storage cabinet, wherein thesequence is generated based on a mapping algorithm. The method includesdetermining whether the first step of the sequence of the one or moresteps is associated with one of the plurality of drawers. The methodincludes, in response to determining that the first step is associatedwith one of the plurality of drawers, automatically unlocking theassociated drawer. The method includes determining whether the firststep is successfully completed. The method includes, in response todetermining that the first step is successfully completed, determiningwhether execution of any additional steps is pending. The methodincludes generating an alert in response to determining that executionof no additional steps is pending. Other aspects include correspondingsystems, apparatus, and computer program products for implementation ofthe method.

In accordance with some implementations, a method includes providing anelectronic medication storage cabinet having a plurality of drawers,each drawer configured with a plurality of removable storage pockets,the drawer configured with a plurality of sensors arranged to identify apositioning of the plurality of removable storage pockets within thedrawer. The method includes receiving an indication of a new medicinecontainer to be stored in the electronic medication storage cabinetwhich requires a new storage pocket to be added to the electronicmedication storage cabinet. The method further includes determining,based on receiving the indication, that at least a subset of removablestorage pockets within one or more of the plurality of drawers requirerepositioning to accommodate the new pocket. The method furthercomprises generating, based on a mapping algorithm, a new arrangement ofthe subset of removable storage pockets and the new pocket within theone or more of the plurality of drawers. At the electronic medicationstorage cabinet, execute a predetermined sequence of steps for effectingthe new arrangement including: (1) automatically unlocking a firstdrawer of the plurality of drawers, (2) providing a first prompt toremove at least a first storage pocket of the subset of removablestorage pockets, (3) verifying, via the plurality of sensors, that thefirst storage pocket was removed, (4) providing a second prompt torelocate the first pocket within a first available space within the oneor more of the plurality of drawers, (5) verifying, via the plurality ofsensors, that the first pocket was relocated, (6) providing a thirdprompt to insert the new pocket within a second available space of theone or more of the plurality of drawers, and (7) verifying, via theplurality of sensors, that the new pocket was inserted. Other aspectsinclude corresponding systems, apparatus, and computer program productsfor implementation of the method.

In accordance with some implementations, an electronic medicationstorage cabinet includes one or more processors and memory storing oneor more programs configured for execution by the one or more processors.The one or more programs include instructions for performing theoperations of any of the methods described in this application. Inaccordance with some implementations, a non-transitory computer-readablestorage medium stores instructions that, when executed by a serversystem, cause the server system to perform the operations of any of themethods described in this application.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described implementations,reference should be made to the Description of Implementations below, inconjunction with the following drawings. Like reference numerals referto corresponding parts throughout the figures and description.

FIG. 1A is a block diagram of a network architecture for loadoptimization of medication into electronic medication storage unitaccording to illustrative implementations.

FIG. 1B is a front view of an electronic medication storage cabinetaccording to illustrative implementations.

FIG. 1C is top view of a drawer of an electronic medication storagecabinet according to illustrative implementations.

FIG. 2 is a block diagram of an exemplary server system from thearchitecture of FIG. 1 according to illustrative implementations.

FIG. 3 is a block diagram of an exemplary client device from thearchitecture of FIG. 1 according to illustrative implementations.

FIGS. 4A-4D are flow charts of an example method of identifying alocation to store a medication into an electronic medication storagecabinet according to illustrative implementations.

FIGS. 5A-5B are flow charts of an example method of loading a medicationinto an electronic medication storage cabinet, according to illustrativeimplementations.

In one or more implementations, not all of the depicted components ineach figure may be required, and one or more implementations may includeadditional components not shown in a figure. Variations in thearrangement and type of the components may be made without departingfrom the scope of the subject disclosure. Additional components,different components, or fewer components may be utilized within thescope of the subject disclosure.

DETAILED DESCRIPTION

The detailed description set forth below is intended as a description ofvarious configurations of the subject disclosure and is not intended torepresent the only configurations in which the subject disclosure may bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a thorough understandingof the subject disclosure. However, it will be apparent to those skilledin the art that the subject disclosure may be practiced without thesespecific details. In some instances, structures and components are shownin block diagram form in order to avoid obscuring the concepts of thesubject disclosure. Like components are labeled with identical elementnumbers for ease of understanding.

It will also be understood that, although the terms “first” and “second”are used herein to describe various elements, these elements should notbe limited by these terms. These terms are used only to distinguish oneelement from another. For example, a first drawer could be termed asecond drawer, and, similarly, a second drawer could be termed a firstdrawer, without departing from the scope of the various describedimplementations. The first drawer and the second drawer are bothdrawers, but they are not the same drawer.

The terminology used in the description of the various implementationsdescribed herein is for the purpose of describing particularimplementations only and is not intended to be limiting. As used in thedescription of the various described implementations and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed terms. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising” when used in the specification, specify the presence ofstated features, steps, operations, elements, and/or components, but donot preclude the presence or addition of one or more other features,steps, operations, elements, components, and/or groups thereof.

FIG. 1 is a block diagram of a network architecture 100 in accordancewith some embodiments.

The network architecture 100 includes one or more electronic medicationstorage cabinets 104-1, 104-2, . . . , 104-n, collectively referred toherein as electronic medication storage cabinets 104. In someimplementations, an electronic medication storage cabinet 104 may becommunicatively and/or operably coupled to one or more otherelectronically controlled and/or managed medication storage units, suchas electronically controlled and/or managed medication storage towers,electronically controlled and/or managed medication storagerefrigerators, and the like.

The one or more electronic medication storage cabinets 104 may becommunicatively coupled to an electronic medication storage systemserver 108 by one or more communication networks 106. The electronicmedication storage system server 108 may be communicatively coupled toone or more patient and/or medication related systems 110-1, 110-2, . .. , 110-m, collectively referred to herein as medication systems 110, byone or more communication networks 106. The one or more medicationssystems 110 may be any system configured to store, maintain, and/orupdate data related to active and/or discharged patients, locations ofthe patients (e.g., within a healthcare facility), medication orders forthe patients, and the like. Examples of medication systems 110 include,but are not limited to, an electronic medical record system, a pharmacyinformation system, and the like. In some implementations, theelectronic medication storage cabinets 104 may be communicativelycoupled to the medication systems 110 via the electronic medicationstorage system server 108. In some implementations, the electronicmedication storage cabinets 104 may be communicatively coupled to themedication systems 110 by the one or more communication networks 106.

Examples of the one or more communication networks 106 include, but arenot limited to, an intranet, the Internet, cellular telephone networks,mobile data networks, wide area networks, local area networks,metropolitan area networks, and the like. In some implementations, theone or more communication networks 106 include a public communicationnetwork (e.g., the Internet and/or a cellular data network), a privatecommunications network (e.g., a private LAN or leased lines), or acombination of such communication networks. The electronic medicationstorage cabinets 104 may be configured to communicate with theelectronic medication storage system server 108 and/or the medicationsystems 110. In some implementations, the electronic medication storagecabinets 104 may be configured to receive and/or transfer patient and/ormedication related data from the electronic medication storage systemserver 108 or medication systems 110. Examples of patient related datainclude, but are not limited to, patient biographical information,electronic medical records, information related to one or more recentprocedures or treatment, information related to any prescribedmedication, and the like. Examples of medication related data include,but are not limited to, medications stored in the electronic medicationstorage cabinets 104, location of medications stored in the electronicmedication storage cabinets 104, and the like.

In some implementations, the electronic medication storage system server108 is a single computing device such as a computer server, while inother implementations, the electronic medication storage system server108 is implemented by multiple computing devices working together toperform the actions of a server system (e.g., cloud computing).Additional details of the electronic medication storage system server108 are described herein and with reference to FIG. 2.

The electronic medication storage cabinets 104 may include one or moreinput devices (shown in FIG. 3) configured to receive inputs to theelectronic medication storage cabinets 104. The users 102-1, 102-2, . .. , 102-n, collectively referred to herein as users 102, may interactwith the one or more electronic medication storage cabinets 104 via theone or more input devices. The users 102 may utilize the electronicmedication storage cabinets 104 to access the electronic medicationstorage system server 108 and/or medication systems 110 to participatein corresponding services provided by the electronic medication storagesystem server 108 and/or medication systems 110.

The electronic medication storage cabinets 104 may include one or moreelectronically controlled and/or managed movable drawers. For example,as shown in FIG. 1B, the electronic medication storage cabinet 104-1includes electronically controlled and/or managed movable drawers 120 a,120 b, 120 c, 120 d, 120 e, 120 f, 120 g, 120 h, 120 i, collectivelyreferred to herein as movable drawers 120. FIG. 1B is a front view ofthe electronic medication storage cabinet 104-1. In someimplementations, some movable drawers 120 may be of different sizes. Insome implementations, the electronic medication storage cabinets 104 maybe configured to associate one or more movable drawers 120 with one ormore patients. For example, the electronic medication storage cabinet104-1 may be configured to associate movable drawer 120 a with a firstpatient, and movable drawer 120 c with a second patient. In someimplementations, the electronic medication storage cabinets 104 may beconfigured to associate one movable drawer 120 with multiple patients.For example, the electronic medication storage cabinet 104-1 may beconfigured to associate movable drawer 120 c with the second patient anda fourth patient. In some implementations, the electronic medicationstorage cabinets 104 may be configured to associate a patient with oneor more movable drawers 120 based on the medications stored in a movabledrawer 120. For example, if a patient is prescribed a medication or isassociated with a medication, the electronic medication storage cabinet104 may be configured to associate the patient with a drawer thatcomprises the prescribed medication.

The movable drawers 120 may include or be configured with one or moresensor devices (not shown in FIG. 1B). For example, movable drawers 120may be configured with sensor devices on the inside portions of thefloors of the movable drawers 120. In some implementations, the sensordevices may be placed in one or more patterns at different locationswithin the movable drawers 120. Examples of such patterns include, butare not limited to, grid patterns, and the like. In someimplementations, the sensor devices may be placed in a grid patterncovering a major portion of the movable drawers 120. For example, thesensor devices may be placed in a grid pattern covering at least amajority of the inside floor of the movable drawers 120.

Each movable drawer 120 may have one or more pockets. For example, asshown in FIG. 1C, the movable drawer 120 a includes pockets 130 a, 130b, 130 c, 130 d, 130 e, 130 f, 130 g, 130 h, 130 i, 130 j, 130 k, 1301,130 m, 130 n, 130 o, and 130 p, collectively referred to herein aspockets 130. FIG. 1C is a top view of the movable drawer 120 a. In someimplementations, the pockets 130 may be different sizes and shapes. Insome implementations, one or more pockets 130 may be fixed to aparticular location within the movable drawer 120. Such pockets 130 arereferred to herein as fixed pockets. In some implementations, one ormore pockets 130 may be movable from a first location within the movabledrawer 120 to a second location within the movable drawer 120, and/orrelocated to a different movable drawer 120 within the same cabinet alsoconfigured for movable pockets, and/or removed from the movable drawer120. Such pockets 130 may be referred to herein as dynamic pockets. Insome implementations, a dynamic pocket may be moved to a drawer ofanother cabinet configured for movable pockets. In some implementations,contents of a pocket 130 of one type (e.g., dynamic or fixed) may betransferred to a pocket of the other type (e.g., fixed or dynamic) inthe same cabinet. For example, the contents of a fixed type pocket 130may be transferred to a dynamic type pocket 130. Similarly, the contentsof a dynamic type pocket 130 may be transferred to a fixed type pocket130.

The pockets 130 may include or be configured with transmitter devices(not shown in FIG. 1B). In some implementations, the transmitter devicesof the pockets 130 may be light based transmitter devices (e.g., laserbased transmitter, and the like). In some implementations, the pockets130 may include radio-frequency identification (RFID) based electronicdevices (e.g., RFID tags).

In some implementations, pockets 130 may be either assigned to contain asingle medication for use by multiple patients (“medication-specific”),a plurality of medications for use by a specific patient(“patient-specific”), or a single medication which may be a controlledsubstance for use only by a specific patient (“patient-specificcontrolled substance”).

Turning now to FIG. 2, there is shown a block diagram depicting anelectronic medication storage system server 108 in accordance with someimplementations. The electronic medication storage system server 108typically includes one or more processing units (processors or cores)202, one or more network or other communications interfaces 204, memory206, and one or more communication buses 208 for interconnecting thesecomponents. The communication buses 208 optionally include circuitry(sometimes called a chipset) that interconnects and controlscommunications between system components. In some implementations, theelectronic medication storage system server 108 may include a displaydevice 212. In some implementations, the electronic medication storagesystem server 108 may include input devices such as a keyboard, a mouse,a trackpad, and/or input buttons. In some implementations, the displaydevice 212 may include a touch-sensitive surface, in which case thedisplay is a touch-sensitive display.

In some implementations, the electronic medication storage system server108 may be configured to receive data related to patients, pockets 130,movable drawers 120, and the like, from the electronic medicationstorage cabinets 104. In some implementations, the electronic medicationstorage system server 108 may be configured to transmit data related tooptimized processes of loading ordered medications to electronicmedication storage cabinets 104. The electronic medication storagesystem server 108 may be configured to receive data related to orderedmedications for patients, for loading into electronic medication storagecabinets 104, and the like, from medication systems 110. The electronicmedication storage system server 108 may be configured to transmit datarelated to dispensing of medication in medication containers, statusindicating success or failure of loading the ordered medications intothe electronic medication storage cabinets 104, and the like, to themedication systems 110. In some implementations, the electronicmedication storage system server 108 may be located either on premisesof a healthcare organization, remotely hosted by a third-party serviceprovider (e.g., in a cloud computing environment), and/or a combinationthereof.

The electronic medication storage system server 108 may be configuredwith a mapping algorithm that is configured to identify a location in anelectronic medication storage cabinet to store a medication and/or amedicine container containing the medication. In some implementations,the medicine container may be a dynamic pocket described herein. The oneor more processes of the mapping algorithm are described herein withreference to FIGS. 4A-4D. The electronic medication storage systemserver 108 may generate a sequence of one or more steps to load themedication and/or the medicine container into the identified location ofan electronic medication storage cabinet based on the mapping algorithm.

The memory 206 may be a high-speed random-access memory, such as DRAM,SRAM, DDR RAM, or other random-access solid-state memory devices, andmay include non-volatile memory, such as one or more magnetic diskstorage devices, optical disk storage devices, flash memory devices,and/or other non-volatile solid-state storage devices. In someimplementations, the memory 206 includes one or more storage devicesremotely located from the processor(s) 202. The memory 206, oralternatively the non-volatile memory device(s) within the memory 206,includes a non-transitory computer-readable storage medium. In someimplementations, the memory 206 or the computer-readable storage mediumof the memory 206 stores programs, modules, and/or data structures thatmay be used for the performing one or more operations of the serversystem 108. The electronic storage system server 108 may execute themapping algorithm based on one or more modules described herein and/orincluded in the memory 206. For example, the memory 206 may includeprograms, modules, and/or data structures for an operating system 226, anetwork communication module 228, a patient information module 232, anaccess device module 238, a storage identification module 234, a pocketmapping module 242, a pocket arrangement module 246.

In some implementations, the operating system 226 module may includeprocedures for handling various basic system services and for performinghardware dependent tasks. The network communication module 228 may beconfigured for connecting the server system 108 to other computingdevices via the one or more communication network interfaces 204 (wiredor wireless) and one or more communication networks 106. The patientinformation module 232 may be configured to store data related topatients including, but not limited to, medical history, prescriptionmedication, allergies, and the like. The patient information module 232may be configured to associate a patient with an electronic medicationstorage cabinet 104, and store the association in memory 206. The accessmodule 238 may be configured to grant, deny, and/or modify access to theserver system 108 and/or one or other computing systems or devicescommunicatively coupled to the server system 108.

The storage identification module 234 may be configured to store,maintain, and/or update data related to the contents of every pocket 130for each electronic medication storage cabinet 104 communicativelycoupled to the electronic medication storage system server 108. Thestorage identification module 234 may be configured to store, maintain,and/or update data related to every empty pocket 130 for each electronicmedication storage cabinet 104 communicatively coupled to the electronicmedication storage system server 108. The electronic medication storagesystem 108 may receive data related to contents of pocket 130 from theelectronic medication storage cabinets 104, and the storageidentification module 234 may be configured to maintain and/or updatedata related to contents of pocket 130 based on the data received fromthe electronic medication storage cabinets 104. In some implementations,storage identification module 234 may be similarly configured as storageidentification module 334 described below with reference to FIG. 3.

For each electronic medication storage cabinet 104 communicativelycoupled to the electronic medication storage system server 108, thepocket mapping module 242 may be configured to associate the dynamicand/or fixed pockets 130 of each movable drawer 120 with correspondinglocations in the movable drawer 120, and store the associations inmemory 206. In some implementations, the pocket mapping module 242 maybe configured to receive data related to sensors with their locations indrawers 120 for each electronic medication storage cabinet 104, andbased on the mapping, the pocket mapping module 242 may be configured todetermine locations of pockets within the drawers 120. In someimplementations, the pocket mapping module 242 may be similarlyconfigured as the pocket mapping module 342 described below withreference to FIG. 3.

The pocket arrangement module 246 may be configured to determineprocesses to rearrange one or more dynamic pockets 130 in the electronicmedication storage cabinets 104 based on dimensions and/or size of otherdynamic pockets 130 in the electronic medication storage cabinets 104and/or a new dynamic pocket 130 comprising a newly ordered medication.The pocket arrangement module 246 may be similarly configured as pocketarrangement module 346 described below with reference to FIG. 3.

Each of the above identified modules and applications corresponds to aset of executable instructions for performing one or more functions asdescribed above and/or in the methods described in this application(e.g., the computer-implemented methods and other information processingmethods described herein). These modules (i.e., sets of instructions)need not be implemented as separate software programs, procedures ormodules, and thus various subsets of these modules are, optionally,combined or otherwise re-arranged in various implementations. In someimplementations, the memory 206 may store a subset of the modules anddata structures identified above. In some implementations, the memory206 may store additional modules and data structures not describedabove. Processors 202 may be configured to execute the above identifiedmodules for performing the one or more above-described functions and/ortechniques of optimizing loading of medications in electronic medicationstorage cabinet 104 as described herein with reference to FIGS. 4A-4D.

Turning now to FIG. 3, there is shown a block diagram depicting anelectronic medication storage cabinet 104. An electronic medicationstorage cabinet 104 may include one or more processors 302, one or morenetwork or communications interfaces 304, memory 306, one or morecommunication buses 308, a user interface unit 310, transmitter devices322, sensor devices 323. The one or more processors 302, the one or morenetwork or communication interfaces 304, memory 306, and the userinterface unit 310 may be configured to communicate with one another viathe one or more communication buses 308. In some implementations, thecommunication buses 308 may include circuitry (sometimes called achipset) that interconnects and controls communications betweencomponents of the electronic medication storage cabinet 104. In someimplementations, the electronic medication storage cabinet 104 mayinclude an image/video capture device 324, such as a camera.

In some implementations, the electronic medication storage cabinet 104may be configured with the mapping algorithm, and one or more processors302 of the electronic medication storage cabinet 104 may be configuredto identify a location in the electronic medication storage cabinet 104to store a medication and/or a medicine container containing themedication. In some implementations, the medicine container may be adynamic pocket described herein. As described above, the one or moreprocesses of the mapping algorithm are described herein with referenceto FIGS. 4A-4D. The electronic medication storage cabinet 104 maygenerate a sequence of one or more steps to load the medication and/orthe medicine container into the identified location of an electronicmedication storage cabinet based on the mapping algorithm.

The user interface unit 310 may include a display 312, one or more inputdevices 316, such as a keyboard or a mouse, one or more audio outputdevices 318, and/or one or more audio input devices 320. In someimplementations, the display 312 may include a touch sensitive displayor surface 314, which is configured to receive inputs from a user 102.The one or more audio output devices 318 may include, but are notlimited to, speakers, interfaces configured to transfer audio relateddata to a device configured to project audio, and the like. The one ormore input devices 320 may include, but are not limited to, microphones,interfaces configured to receive audio related data from a deviceconfigured to receive audio.

The movable drawers 120 of the electronic medication storage cabinet 104may include or be configured with one or more sensor devices, such assensor devices 323. For example, movable drawers 120 may be configuredwith sensor devices 323 on the inside portions of the floors of themovable drawers 120. In some implementations, the sensor devices may beplaced in one or more patterns at different locations within the movabledrawers 120. Examples of such patterns include, but are not limited to,grid patterns, and the like. In some implementations, the sensor devicesmay be placed in a grid pattern covering a major portion of the movabledrawers 120. For example, the sensor devices may be placed in a gridpattern, forming a grid array of sensors, covering at least a majorityof the inside floor of the movable drawers 120. In some implementations,the sensor devices 323 may be placed around a perimeter of the movabledrawer 120 such that they from a grid of light or signals.

The pockets 130 may include or be configured with transmitter devices,such as transmitter devices 322. In some implementations, thetransmitter devices 322 may be light based transmitter devices (e.g.,laser based transmitter, and the like). In some implementations, thetransmitter devices 322 may be radio-frequency identification (RFID)based devices (e.g., RFID tags).

The sensor devices 323 may be configured to receive signals from thetransmitter devices 322 and output signals based on signals receivedfrom transmitter devices 322. For example, a sensor device 323 may beconfigured to detect whether a transmitter device 322 is placed near thesensor device 323 based on a signal received from the transmitter device322 and produce a signal indicating that a pocket associated with thattransmitter device 322 is placed near that sensor device 323.

The one or more modules (e.g. the pocket mapping module 342) describedherein, and/or processor 302, may be configured to determine a locationof a pocket 130 within the electronic medication storage cabinet 104based on the signals or output data from sensors 323. For example, ifthe sensor devices 323 are placed in a grid pattern, forming a gridarray of sensors, in a movable drawer 120, then based on sensor devices323 in the grid pattern that detect a signal from the transmitter deviceassociated with the pocket 130, the one or more modules (e.g., thepocket mapping module 342) may be configured to determine the locationof the pocket 130 on the grid array of sensor devices 323 and within thedrawer 120. Similarly, based on the signals or output data from thesensor devices 323, the one or more modules (e.g. the pocket mappingmodule 342) may be configured to determine if a pocket 130 has beenremoved from its current location within the electronic medicationstorage cabinet 104. Similarly, based on the signals or output data fromthe sensor devices 323, the one or more modules (e.g. the pocket mappingmodule 342) may be configured to determine if a pocket 130 has beenplaced in a certain or new location within the electronic medicationstorage cabinet 104.

The memory 306 includes high-speed random-access memory, such as DRAM,SRAM, DDR RAM or other random-access solid-state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid-state storage devices. In some implementations, thememory 306 includes one or more storage devices remotely located fromthe processor(s) 302. The memory 306, or alternatively the non-volatilememory device(s) within the memory 306, includes a non-transitorycomputer-readable storage medium. In some implementations, the memory306 or the computer-readable storage medium of the memory 306 stores theprograms, modules, and data structures that may be used for performingoperations of the electronic medication storage cabinets 104 and forperforming techniques described herein for optimization of loading orone or more medications into an electronic medication storage cabinet.In some implementations, the electronic storage cabinet 104 may executethe mapping algorithm based on one or more modules described hereinand/or included in the memory 306. The memory 306 may include anoperating system 326, a network communication module 328, an image/videocapture module 330, an audio input/output module 332, a storageidentification module 334, an access module 338, a pocket mapping module342, a pocket arrangement module 346, and/or a patient informationmodule 348.

The operating system 326 may be configured to perform procedures ofexecution of various system services of the electronic medicationstorage cabinet 104, including, but not limited to, hardware, andsoftware dependent tasks. The network communication module 328 may beconfigured to execute instructions to connect the electronic medicationstorage cabinet 104 to one or more other computing devices, such as thehealthcare server system 108, third party servers 110, and the like, viathe one or more communication interfaces 304 and communication networks,such as the communication network 106. The image/video capture module330 may be configured to execute instructions to capture images or acontinuous stream of images. The audio input module 332 may beconfigured process received input data and transmit instructions and/orrelated data to one or more other components of the electronicmedication storage cabinet 104. The access module 338 may be configuredgrant, deny, and/or modify access to the electronic medication storagecabinet 104. For example, the access module 338 may be configured togrant or deny access to the electronic medication storage cabinet 104based on received login credentials for the electronic medicationstorage cabinet 104.

The storage identification module 334 may be configured for storing alist of empty pockets 130 within the electronic medication storagecabinet 104. In some implementations, each of the pockets 130 within theelectronic medication storage cabinet 104 may be associated with aunique identifier and the storage identification module 334 may beconfigured to generate and/or update the list of empty pockets with theunique identifiers of the pockets 130 that are empty. As describedabove, the pockets 130 may include transmitter devices 322 that are RFIDtags, and in some implementations, the RFID tag of the pocket mayinclude data related to medication within the pocket 130.

The pocket mapping module 342 may be configured to associate the dynamicand/or fixed pockets 130 of the electronic medication storage cabinet104 with locations within a movable drawer 120. In some implementations,the pocket mapping module 342 may be configured to use data from sensordevices 323 located within drawers 120, and/or data from transmitterdevices 322 included within or configured with pockets 130 to determinelocations of the pockets 130 within movable drawers 120. In someimplementations, the pocket mapping module 342 may be configured toassociate a pocket 130 with one or more nearby sensor devices inresponse to the pocket 130 being placed at a particular location withinthe drawer 120.

In some implementations, the pocket mapping module 342 may be configuredto generate a mapping of the sensors with their particular locationwithin the drawer 120, and based on the mapping, the pocket mappingmodule 342 may be configured to determine the location of a particularpocket within the drawer 120. For example, a subset of sensor devices323 of the electronic medication storage cabinet 104-1 may be locatedwithin a movable drawer 120 a, and the pocket mapping module 342 may beconfigured to determine the location of pocket 130 d based on one ormore sensor devices 323 associated with pocket 130 d and the mapping ofthe associated sensor devices 323 with location of the removable drawer120 a. The pocket mapping module 342 may be configured to map amedication with a pocket in which it is stored and store the mapping ofthe medications to pockets in data storage unit.

The pocket arrangement module 346 may be configured to rearrange pockets130 within the electronic medication storage cabinet 104 based ondimensions and/or size of a new pocket 130 and/or ordered medication.The pocket arrangement module 346 may be configured to identify one ormore dynamic pockets in the electronic medication storage cabinet 104,which when rearranged to other drawers 120 or within the same drawer 120will create sufficient contiguous space in one of the drawers 120 toplace the new dynamic pocket 130. For example, based on dimensionsand/or size of a new dynamic pocket 130, the pocket arrangement module346 may identify pocket 130 e and 130 f in drawer 120 a that if moved toa different drawer 120 (e.g., 120 b, 120 c) will create sufficient spacewithin the first drawer 120 a for the new pocket 130. Continuing withthe example, for each of the identified pockets 130 e and 130 f, thepocket arrangement module 346 may be configured to determine, based ontheir respective dimensions and/or size, if sufficient contiguous spaceis available within the other drawers of the electronic medicationstorage cabinet 104 to successfully move the pockets 130 e and 130 ffrom the drawer 120 a a to the other drawers. In some implementations,in response to determining that the identified pockets may besuccessfully moved to other drawers, the pocket arrangement module 346may send a message to the one or more processors 302 indicating that oneor more pockets 130 can be rearranged to create sufficient contiguousspace for the new pocket 130.

The patient information module 348 may be configured to store, and/oraccess patient data of patients associated with the electronicmedication storage cabinet 104. The patient information module 348 maybe configured to store data in and/or access patient data from a datastorage unit of the electronic medication storage cabinet 104 oroperably coupled to the electronic medication storage cabinet 104.Additional details of the load optimization steps and/or techniques aredescribed herein with reference to FIGS. 4A-4D.

Each of the above identified modules and applications corresponds to aset of executable instructions for performing one or more functions asdescribed above and/or in the methods described in this application(e.g., the computer-implemented methods and other information processingmethods described herein). These modules (i.e., sets of instructions)need not be implemented as separate software programs, procedures ormodules, and thus various subsets of these modules are, optionally,combined or otherwise re-arranged in various implementations. In someimplementations, the memory 206 and/or the memory 306 store a subset ofthe modules and data structures identified above. In someimplementations, the memory 206 and/or the memory 306 stores additionalmodules and data structures not described above. Processors 302 may beconfigured to execute the above identified modules for performing theone or more above-described functions and/or techniques of optimizingloading of medications in an electronic medication storage cabinet asdescribed herein with reference to FIGS. 4A-4D.

Turning now to FIGS. 4A-4D, there are shown flowcharts illustrating anoptimized process of identifying a location to store a medication in anelectronic medication storage cabinet. For the purpose of illustrating aclear example, components of the network architecture 100, shown anddescribed with reference to FIG. 1, components of the electronicmedication storage system server 108, shown and described with referenceto FIG. 2, and components of the electronic medication storage cabinets104, shown and described with reference to FIG. 3, may be used todescribe the optimized process of loading a medication in an electronicmedication storage cabinet 104. In some implementations, the optimizedprocess of loading a medication in an electronic medication storagecabinet 104 described herein with reference to FIGS. 4A-4D may beperformed and/or executed by electronic medication storage system server108 via processors 202 and its modules, and in some implementations, byelectronic medication storage cabinet 104 via processors 302 and itsmodules.

The method 400 includes receiving, by one or more processors 202 of theelectronic medication storage system server 108, an order for amedication (block 401). The order for the medication may be received viaa message from a medication system 110. As described above, a medicationsystem 110 may be a medication ordering system and/or a medicationprescribing system, such as an electronic medical record system, apharmacy information system, and the like, of a medical facility, suchas a hospital. In some implementations, the processors 202 may beconfigured to determine, via the patient information module 232, whetherthe medication is ordered for a patient associated with an electronicmedication storage cabinet 104. The one or more processors 202 may beconfigured to determine whether the ordered medication is chosen (e.g.,by a user) to be loaded in the electronic medication storage cabinet 104(block 402). The one or more processors 202 may be configured todetermine whether the ordered medication is chosen to be loaded in theelectronic medication storage cabinet 104 based on a received messagespecifying the ordered medication. The received message may specify thechoice of a user, such as a pharmacist or a pharmacist technician, of amedication system 110 to load the ordered medication into the electronicmedication storage cabinet 104. The user of the medication system 110may provide the choice to load the ordered medication via an input tothe medication system 110, and the medication system 110 may includeinformation related to the choice in the message received by themedication storage cabinet 104. For example, the received messagespecifying the order may include a field that indicates whether themedication is chosen to be stored in the electronic medication storagecabinet or dispensed in some other manner.

If the one or more processors 202 determine that the ordered medicationis chosen not be stored in the electronic medication storage cabinet(NO′ at block 402), then the method 400 proceeds to block 403. At block403, the one or more processors 202 determine that the medication willbe dispensed as a patient specific medication (block 403). In someimplementations, a user, such as a pharmacy technician, may specify forthe ordered medication to be dispensed as a patient specific medicationin electronic medication storage cabinet 104. In some implementations, auser, may provide an input to the electronic medication storage cabinet104 to store the patient specific medication in electronic medicationstorage cabinet 104. For example, a user, when delivering the orderedmedication, may desire to store the medication in the electronicmedication storage cabinet 104 rather than in a different storage area,and may provide an input, to the electronic medication storage cabinet104, to store the ordered medication in the electronic medicationstorage cabinet 104. In such implementations, in response to receivingsuch an input, the one or more processors 302 of the electronicmedication storage cabinet 104 may be configured to transmit a messageto the electronic medication storage system server 108 indicating thatthe ordered medication to be dispensed as patient specific medication,and the one or more processors 202 may initiate the method 400 fromblock 404.

Returning to block 402, if the one or more processors 202 determine thatthe ordered medication is chosen to be stored in the electronicmedication storage cabinet 104, then the method proceeds to block 404.The one or more processors 202 determine whether the ordered medicationcan be stored in the electronic medication storage cabinet 104 (block404). The processors 202 may be configured to determine, based on a setof predetermined rules stored in a memory of the electronic medicationstorage system server 108, whether the ordered medication can be storedin the electronic medication storage cabinet 104. For example, the setof predetermined rules may specify that a set of medications must berefrigerated, and the one or more processors 202 may be configured todetermine that the ordered medication cannot be stored in the electronicmedication storage cabinet 104 if the ordered medication is within theset of medications. Similarly, the set of predetermined rules mayspecify that certain types and/or classification of medications must bestored in a electronically controlled and/or managed storage tower, andthe one or more processors 202 may be configured to determine thatordered medication cannot be stored in the electronic medication storagecabinet 104 if a type or a classification of the ordered medicationmatches one of the specified types or classifications.

If the one or more processors 202 determine that the ordered medicationcannot be stored in the electronic medication storage cabinet 104 (NO′at block 404), then the method 400 proceeds to block 405-a. In someimplementations, in response to the one or more processors 202determining that the ordered medication cannot be stored in theelectronic medication storage cabinet 104, the one or more processors202 maybe configured to generate and transmit an alert to medicationsystem 110. The alert may indicate that the ordered medication cannot beloaded into the electronic medication storage cabinet 104, and may beconfigured to cause the generated alert to be provided and/or displayedto the user (e.g., on a display screen) by sending the alert to themedication system 110.

At block 405-a, the one or processors 202 determine whether the orderedmedication can be refrigerated (block 405-a). As described above, theone or more processors 202 may be configured to determine whether amedication can be refrigerated based on a set of rules. If the one ormore processors 202 determines that the medication can be refrigerated(‘YES’ at block 405-a), then the method 400 proceeds to block 405-b. Theone or more processors 202 transmit a message to medication system 110for storage of the ordered medication in a medication storagerefrigerator (block 405-b). The one or more processors 202 may createsteps to assist a user, such as a pharmacy technician, to load theordered medication in the refrigerator and transmit the created stepsand instructions to electronic medication storage cabinet 104. Asdescribed above, in some implementations, the electronic medicationstorage cabinet 104 may be associated with or communicatively coupled toan electronically controlled and/or managed refrigerator. The one ormore processors 302 may be configured to provide and/or cause thecreated steps to be displayed on a display device associated with theelectronic medication storage cabinet 104 for the user. For example, auser may scan the ordered medication and/or a package containing theordered medication at the electronic medication storage cabinet 104, andthe one or more processors 302 may be configured to provide the receivedcreated steps on a display device associated with the electronicmedication storage cabinet 104.

Returning to block 405-a, if the one or more processors 202 determinethat the ordered medication cannot be refrigerated (‘NO’ at block405-a), then the method 400 continues to block 406-a. At block 406-a,the one or more processors 202 may be configured to determine whetherthe ordered medication can be stored in a tower configured to storemedication (block 406-a). Similar to the refrigerator, in someimplementations, the electronic medication storage cabinet 104 may beassociated with and/or communicatively coupled to an electronicallycontrolled and/or managed medication storage tower. If the one or moreprocessors 202 determine that the ordered medication can be stored inthe electronically controlled and/or managed medication storage tower(‘YES’ at block 406-a), then the method 400 proceeds to block 406-b. Theprocessors 202 transmit a message to the medication system 110 forstorage of the ordered medication in a medication storage tower (block406-b). The one or more processors 202 may be configured to create andtransmit steps and instructions to electronic medication storage cabinet104 to assist a user to store the ordered medication in theelectronically controlled and/or managed tower. If the one or moreprocessors 202 determine that the ordered medication cannot be stored inthe tower (‘NO’ at block 406-a), then the method 400 proceeds to theblock 403. In some implementations, the one or more processors 202 maygenerate an alert that the ordered medication will have to be dispensedas a patient specific medication responsive to the one or moreprocessors 202 determining that the ordered medication cannot be storedin the tower. The alert may be transmitted to the medication system 110.

Returning to block 404, if the one or more processors 202 determine thatthe ordered medication can be stored in the electronic medicationstorage cabinet 104 (‘YES’ at block 404), then the method 400 continuesto block 408. The one or more processors 202 determine whether theordered medication is a patient-specific medication (block 408). In someimplementations, information specifying whether the ordered medicationis a patient-specific medication is received by the electronicmedication storage system server 108, and the one or more processors 202may be configured to determine whether the ordered medication is apatient-specific medication based on the received information. Forexample, the message received from the medication system 110 maycomprise information specifying whether the ordered medication ispatient-specific or not, and the one or more processors 202 determinethat the ordered medication is patient-specific based on the informationin the message.

If the one or more processors 202 determine that the ordered medicationis patient-specific (‘YES’ at block 408), then the method 400 continuesto block 442. Additional details of the method 400 at block 442 aredescribed herein with reference to FIG. 4C. If the one or moreprocessors 202 determine that the ordered medication is notpatient-specific (‘NO’ at block 408), then the method 400 continues toblock 409. At block 409, the one or more processors 202 determinewhether the electronic medication storage cabinet 104 at which theordered medication can be loaded supports dynamic pockets (block 409).In some implementations, configuration data of the electronic medicationstorage cabinet 104 may specify whether the electronic medicationstorage cabinet 104 supports dynamic pockets, and the configuration dataor information related to that configuration data may be stored in theelectronic medication storage system server 108 (e.g., in a storage unitof and/or associated with the electronic medication storage system 108).The one or more processors 202 may be configured to determine whetherthe electronic medication storage cabinet 104 supports dynamic pocketsbased on the configuration data.

If the one or more processors 202 determine that the electronicmedication storage cabinet 104 supports dynamic pockets (‘YES’ at block409), then the method 400 continues to block 410. At block 410, the oneor more processors 202 determine whether the ordered medication can bestored in a dynamic pocket of the electronic medication storage cabinet104. As described above, an electronic medication storage cabinet 104may include dynamic pockets, fixed pockets, and a combination thereof.The one or more processors 202 may be configured to determine whethermedications can be stored in dynamic pockets based on a set of rulesthat specify whether certain medications are permitted to be stored indynamic pockets. For example, the set of rules may specify a list ofidentifiers of medications that may only be stored in certain type ofpockets of an automated drug dispensing cabinet 104, and the one or moreprocessors 202 may be configured to check if an identifier of theordered medication is within the list and determine that the orderedmedication cannot be stored in a dynamic pocket if the identifier of theordered medication is within that specified list. Similarly, the set ofrules may specify that certain types of medications, such as controlledsubstances, may only be stored in secured pockets or pockets with a lid,such as a dynamic pocket in some implementations, and if the one or moreprocessors 202 determines that the ordered medication is such a type ofmedication, then the processors 202 determine that the orderedmedication can be stored in a dynamic pocket.

If the one or more processors 202 determine that the ordered medicationmay be stored in the dynamic pockets of the electronic medicationstorage cabinet 104, then the method 400 proceeds to block 411. The oneor more processors 202 determine current locations of dynamic pockets inthe electronic medication storage cabinet 104 (block 411). As describedabove, the pocket mapping module 242 may be configured to associate thedynamic and/or fixed pockets 130 of the electronic medication storagecabinet 104 with locations within the movable drawers 120. The one ormore processors 202, via the pocket mapping module 242, may determinethe locations of one or more dynamic pockets.

The one or more processors 202 determine a size of a dynamic pocket forthe ordered medication (block 412). A user, such as a pharmacytechnician, after reviewing the medication, may place the orderedmedication in a dynamic pocket, referred to herein as an unassigneddynamic pocket. The unassigned dynamic pocket may be outside of theelectronic medication storage cabinet 104 and not in any drawers 120 ofthe electronic medication storage cabinet 104. In some implementations,the electronic medication storage system server 108 may receive the sizeand/or dimensions of the unassigned dynamic pocket from the medicationsystem 110.

The one or more processors 202 may associate the unassigneddynamic-pocket with the ordered medication. In some implementations, theelectronic medication storage system server 108 may be configured toreceive an identifier of the unassigned dynamic-pocket and an identifierof the ordered medication from the medication system 110, and the one ormore processors 202 may be configured to associate the unassigneddynamic pocket with the ordered medication by associating the respectiveidentifiers with each other. In some implementations, the one or moreprocessors 202 may be configured to access medication system 110 todetermine an identifier of the unassigned dynamic-pocket, and associatethe ordered medication with the identifier of the unassigneddynamic-pocket. In some implementations, the electronic medicationstorage system server 108 may be configured with a set of rules thatspecify sizes and/or dimensions of dynamic pockets for variousmedications (e.g., identifiers of medications). The one or moreprocessors 202, based on the ordered medication (e.g., identifier of theordered medication) and the specified size and/or dimension of dynamicpocket in the set of rules, may be configured to determine size and/ordimensions of an unassigned dynamic pocket for the ordered medication.

The one or more processors 202 determines whether sufficient contiguousspace is available in the electronic medication storage cabinet (block413). In some implementations, the one or more processors 202, viapocket mapping module 242, may be configured to determine the dimensionsof the movable drawers 120 of the electronic medication storage cabinets104. In some implementations, the one or more processors 202, via pocketmapping module 242, may be configured to identify the locations in theelectronic medication storage cabinet 104 that are not associated withany dynamic pockets, and calculate, based on the locations that are notassociated with any dynamic pockets and dimensions of the movabledrawers 120, the amount of contiguous space available in the electronicmedication storage cabinet 104.

In some implementations, the one or more processors 202 may beconfigured to determine whether the calculated amount of contiguousspace satisfies the dimensions and/or size of the unassigned dynamicpocket, and, if the calculated amount of contiguous space satisfies thedimensions and/or size of the unassigned dynamic pocket, then the one ormore processors 202 may be configured to determine that sufficientcontiguous space is available in the electronic medication storagecabinet 104. In some implementations, the one or more processors 202,may provide an alert to user (e.g., via a display device of themedication system 110) that indicates that the ordered medication can bestored in a dynamic pocket if the one or more processors 202 determinethat sufficient contiguous free space is available for the unassigneddynamic pocket.

If the one or more processors 202 determine that sufficient contiguousspace is available in the electronic medication storage cabinet 104(‘YES’ at block 413), then the method 400 proceeds to block 414. Atblock 414, the one or more processors 202 transmit a message to themedication systems 110 indicating that the ordered medication can bedispensed in a dynamic pocket (block 414). In some implementations, theone or more processors 202 may be configured to specify instructions todispense the ordered medications into the unassigned dynamic pocket. Insome implementations, the one or more processors 202 may be configuredto provide the medication system 110 access to an electronicallycontrolled cabinet comprising dynamic pockets. In some implementations,the one or more processors 202 may identify a next available dynamicpocket for use by a user of the medication system 110 and transmit thatinformation to the medication system 110.

In some implementations, the one or more processors 202, via the pocketmapping module 242, may be configured to assign one or more contiguouslocations in the electronic medication storage cabinet 104 with theunassigned dynamic pocket. The one or more processors 202 create stepsto place the unassigned dynamic pocket in the electronic medicationstorage cabinet 104 (block 415). The created steps may be sequentialgraphical steps. In some implementations, the one or more processors 202generate an alert that the unassigned dynamic pocket is assigned spacein the electronic medication storage cabinet 104. In someimplementations, the one or more processors 202 may associate thecreated steps with the ordered medication and/or the unassigned dynamicpocket, and store the association in a storage unit of the electronicmedication storage system server 108. The one or more processors 202 maybe configured to transmit the created steps associated with an orderedmedication and/or an unassigned dynamic pocket to electronic medicationstorage cabinet 104. As described below, the created steps may bedisplayed on a display device, such as display device 312, when theordered medication is delivered to the electronic medication storagecabinet 104. Additional details of delivering an ordered medication tothe electronic medication storage cabinet 104 are described herein inwith reference to FIGS. 5A and 5B. The method 400 proceeds to block 490.The one or more processors 202 schedule the ordered medication fordelivery to the electronic medication storage cabinet 104 (block 490).In some implementations, the one or more processors 202 may beconfigured to store data related to whether an ordered medication issuccessfully delivered to the electronic medication storage cabinet 104.In some implementations, the one or more processors 202 may transmitinstructions to the electronic medication storage cabinet 104 indicatingthat an ordered medication is scheduled to be delivered to theelectronic medication storage cabinet 104.

Returning to block 413, if the one or more processors 202 determine thatsufficient contiguous space is not available (‘NO’ at block 413), thenthe method 400 proceeds to block 416. The one or more processors 202determine whether any dynamic-pockets can be reorganized to create thesufficient contiguous space (block 416). For example, the one or moreprocessors 202, via pocket arrangement module 246, may be configured todetermine if sufficient contiguous space can be created in theelectronic medication storage cabinet 104 by reorganizing or rearrangingthe one or more dynamic-pockets that are in the electronic medicationstorage cabinet 104. If sufficient contiguous space can be created byreorganizing the dynamic pockets, then the one or more processors 202determine that dynamic-pockets can be reorganized. If the one or moreprocessors 202 determine that one or more dynamic pockets can bereorganized to create sufficient contiguous space (‘YES’ at block 416),then the method 400 proceeds to block 417. At block 417, similar toblock 414, the one or more processors 202 transmit a message to themedication system 110 indicating that the ordered medication can bedispensed or placed in a dynamic pocket.

The one or more processors 202 create steps to rearrange thedynamic-pockets (block 418). Similar to the created steps to place theunassigned dynamic pocket in the electronic medication storage cabinet104, the created steps to rearrange the dynamic-pockets may begraphical, and the one or more processors 202, may be configured totransmit the created steps to the electronic medication storage cabinet104. The one or more processors 202 create steps to place the unassigneddynamic pocket in the electronic medication storage cabinet 104 (block419). The one or more processors 202 may be configured to transmit thecreated steps of placing the unassigned dynamic pocket in the electronicmedication storage cabinet 104 to the electronic medication storagecabinet 104. The method 400 proceeds to block 490. The one or moreprocessors 202 schedule the ordered medication for delivery to theelectronic medication storage cabinet 104 (block 490).

Returning to block 416, if the one or more processors 202 determine thatsufficient contiguous space is not available (NO′ at block 416), thenthe method 400 proceeds to block 420. The one or more processors 202determine whether contents of a dynamic pocket in the electronicmedication storage cabinet 104 can be combined with contents of anotherdynamic pocket of in the electronic medication storage cabinet 104(block 420). In some implementations, the one or more processors 202 maybe configured to determine that contents of a first dynamic pocket canbe combined with contents of another dynamic pocket if a uniqueidentifier of the medication in the first dynamic pocket is the same asa unique identifier of the medication in another dynamic pocket. In someimplementations, the one or more processors 202 may be configured todetermine the unique identifier of a medication based on received datarelated to the medications from the medication systems 110 and/orelectronic medication storage cabinet 104. The electronic medicationstorage system server 108 may receive data related to a medication and apocket 130 in which it is placed in an electronic medication storagecabinet 104 and store the data in a storage unit associated with theelectronic medication storage system server 108. Based on such data, theone or more processors 202 may be configured to determine the pocketsthat contain medications with the same identifiers.

If the one or more processors 202 determine that the contents of thedynamic pocket can be combined with contents of another dynamic pocket,then the method 400 proceeds to block 421. At block 421, similar toblocks 414 and 417, the one or more processors 202 transmit a message tothe medication system 110 indicating that the ordered medication can bedispensed or placed in a dynamic pocket.

The one or more processors 202 create steps to combine dynamic pockets(block 422). For example, the one or more processors 202, via pocketmapping module 242, may be configured to create steps to combinemedication of one dynamic-pocket with medication of anotherdynamic-pocket. The one or more processors 202 create steps to removethe freed or the empty dynamic-pocket in the electronic medicationstorage cabinet 104 (block 423). The one or more processors 202 createsteps to place the unassigned dynamic-pocket in the electronicmedication storage cabinet 104 (block 424). The one or more processors302 may create steps to place the unassigned dynamic-pocket in alocation of the freed dynamic pocket in the electronic medicationstorage cabinet 104. The method 400 proceeds to block 490. The one ormore processors 202 schedule the ordered medication for delivery to theelectronic medication storage cabinet 104 (block 490).

Returning to block 420, if the one or more processors 202 determine thatthe contents of a dynamic pocket in the electronic medication storagecabinet 104 cannot be combined with contents of another dynamic pocketof in the electronic medication storage cabinet 104 (‘NO’ at block 420),then the method 400 proceeds to block 425. The one or more processors202 determine whether current inventory in any dynamic pockets can beremoved. (block 425). To determine whether current inventory may beremoved from pockets of the electronic medication storage cabinet 104,the one or more processors 202 may be configured to determine whetherthere are any patient-specific medications for patients who weretransferred or discharged from the medical facility or a unit of medicalfacility (block 449 in FIG. 4D). In some implementations, eachpatient-specific medication may be associated with a patient for whomthe medication is ordered. The associations may be stored in a storageunit associated with the electronic medication storage system server 108and/or electronic medication storage cabinet 104. The one or moreprocessors 202, based on the stored associations, may determine if anyof the medications in the pockets are associated with transferred out ordischarged patients.

If the one or more processors 202 determines that a pocket 130 in theelectronic medication storage cabinet 104 includes medications fortransferred or discharged patients (‘YES’ at block 449), then the method400 proceeds to block 450. At block 450, the one or more processors 202determine that the patient-specific medication can be removed. The oneor more processors 202 may be configured to create steps for removal ofpatient-specific medication and transfer the steps to the electronicmedication storage cabinet 104. If the one or more processors 202determine that the electronic medication storage cabinet 104 does notinclude any patient-specific medications for transferred or dischargedpatients (NO′ at block 449), then the method 400 proceeds to block 451.The one or more processors 202 determine whether any pockets in theelectronic medication storage cabinet 104 include any discontinuedmedication (block 451). In some implementations, a set of rules mayspecify a list of patient-specific medication that are discontinued, andthe one or more processors 202 may be configured to determine that apatient-specific medication in a pocket is discontinued if themedication matches a medication in the specified list.

If the one or more processors 202 determine that a pocket includes adiscontinued medication (‘YES’ at block 451), then the method 400proceeds to block 452. The one or more processors 202 determine that thepatient-specific medication can be removed. The one or more processors202, similar to block 450, may be configured to create steps for removalof patient-specific medication and transfer the steps to the electronicmedication storage cabinet 104. If the one or more processors 202determine that the discontinued medications are not stored in theelectronic medication storage cabinet 104 (‘NO’ at block 451), then themethod 400 proceeds to block 453. At block 453, the one or moreprocessors 202 determine whether a medication in a pocket 130 of theelectronic medication storage cabinet is a standard stock item. In someimplementations, a set of rules may specify a list of medications thatare predetermined to be standard stock type of medications, and the oneor more processors 202 may determine if a medication in a pocket isstandard stock based on the specified list of medications.

If the one or more processors 202 determine that the medication in thepocket 130 is of a standard stock type (‘YES’ at block 453), then themethod 400 proceeds to block 458. The one or more processors 202determine that the medication should not be removed from the electronicmedication storage cabinet 104 (block 458). If the one or moreprocessors 202 determine that the medication in the pocket is not of astandard stock type (‘NO’ at block 453), then the method 400 proceeds toblock 454. The one or more processors 202 determine whether there areany active orders for a medication in a pocket 130 at an electronicmedication storage cabinet 104 (block 454). In some implementations, theone or more processors 202 may store and update a list of current activeorders and corresponding medications for the orders in a storage unit ofthe electronic medication storage cabinet 104. In some implementations,the one or more processors 202 may determine whether there are anyactive orders for a medication based on the stored list specifying thecurrent active orders.

If the one or more processors 202 determine there is an active order fora medication (‘YES’ at block 454), then the proceeds to block 458, andthe one or more processors 202 determine that the medication cannot beremoved (block 458). If the one or more processors 202 determine thereare no active orders for medications in any pocket 130 of the electronicmedication storage cabinet 104 (NO′ at block 454), then the method 400proceeds to block 455. The one or more processors 202 determine if anyof the medications are potentially expired in the electronic medicationstorage cabinet 104 (block 455). If the one or more processors 202determine that there are medications that may be potentially expired inthe electronic medication storage cabinet 104 (‘YES’ at block 455), thenthe method proceeds to block 456, and the one or more processors 202determine that the expired medication can be removed. The one or moreprocessors 202 may be configured to create steps to remove the expiredmedication from the electronic medication storage cabinet 104 andtransmit the created steps to the electronic medication storage cabinet104. If the one or more processors 202 determine that there are nomedications in any pockets 130 of the electronic medication storagecabinet 104 that are potentially expired (‘NO’ at block 455), then themethod 400 proceeds to block 457.

The one or more processors 202 determine if a medication in a pocket 130has been withdrawn and/or used for a patient within a threshold numberof days (block 457). The one or processors 202 may receive data formedications stored in electronic medication storage cabinets 104 thatwere used for patients and a date and time at which they were used, andbased on such data, the one or more processors 202 may be configured todetermine whether a medication in an electronic medication storagecabinet 104 has been withdrawn and/or used for a patient within thethreshold number of days. If the one or more processors 202 determinesthat the medication in a pocket has been withdrawn and/or used within athreshold number of days (‘YES’ at block 457), then the method 400proceeds to block 458, and the one or more processors 202 determinesthat the medication cannot be removed (block 458). If the one or moreprocessors 202 determines that the medication in the pocket 130 has notbeen withdrawn and/or used within a threshold number of days (‘NO’ atblock 457), then the method 400 proceeds to block 459. The one or moreprocessors 202 determine that the medication in the pocket 130 can beremoved (block 459).

Returning to block 425 in FIG. 4B, if the one or more processors 202determine that inventory in a dynamic pocket 130 can be removed (‘YES’at block 425), then the method proceeds to block 426. At block 426,similar to blocks 414, 417, 421, the one or more processors 202 transmita message to the medication system 110 indicating that the orderedmedication can be dispensed or placed in a dynamic pocket.

The one or more processors 202 create steps to remove one or moredynamic pockets that include inventory (e.g., medications) that can beremoved (block 427). The one or more processors 202 may transmit thecreated steps to remove the one or more dynamic pockets to theelectronic medication storage cabinet 104. The one or more processors202 create steps to place the unassigned dynamic pocket in theelectronic medication storage cabinet 104 (block 428). The created stepsmay indicate that the unassigned dynamic pocket may be placed in thesame location as the dynamic pocket that was removed. The one or moreprocessors 202 may be configured to transmit to the electronicmedication storage cabinet 104, the created steps to place theunassigned dynamic pocket in the electronic medication storage cabinet104. The method 400 proceeds to block 490. The one or more processors202 schedule the ordered medication for delivery to the electronicmedication storage cabinet 104 (block 490).

Returning to block 425, if the one or more processors 202 determine thatcurrent inventory in any dynamic pockets 130 cannot be removed (‘NO’ atblock 425), then the method proceeds to block 430. In someimplementations, at block 425, if the one or more processors 202determine that current inventory in any dynamic pockets 130 cannot beremoved, then the one or more processors 202 may be configured totransmit a message to medication systems 110 indicating that the orderedmedication cannot be dispensed and/or placed in a dynamic pocket in theelectronic medication storage cabinet 104

Returning to block 410, if the one or more processors 202 determine thatthe medications cannot be stored in a dynamic pocket (‘NO’ at block410), then the method 400 proceeds to block 430. And at block 409, ifthe one or more processors 202 determine that the electronic medicationstorage cabinet 104 does not support any dynamic pockets (‘NO’ at block409), then the method 400 proceeds to block 430.

At block 430, the one or more processors 202 determine whether a validfixed pocket is available. In some implementations, the one or moreprocessors 202 may be configured to determine that a valid fixed-pocketis available if the list of empty pockets stored by the storageidentification module 234 includes the fixed-pocket. If the one or moreprocessors 202 determine that a valid fixed-pocket is available (‘YES’at block 430), then the method proceeds to block 431. The one or moreprocessors 202 assigns the valid-fixed pocket to the ordered medication(block 431). The one or more processors 202 may be configured toassociate the ordered medication with the assigned valid fixed-pocketand store the mapping in a storage unit.

The one or more processors 202 transmit a message to the medicationsystems 110 indicating that the ordered medication can be dispensed in abaggie (block 432). The term “baggie” as used herein may be any type ofa container to hold a medication. The one or more processors 202 createsteps to fill the valid fixed-pocket (block 433). The one or moreprocessors 202 may be configured to create the steps based on certaincharacteristics of the fixed pocket. For example, if the fixed pocket isconfigured with a lid, then the one or more processors 202 may create astep to open the lid and the close lid after the ordered is successfullyplaced in the pocket. Similarly, if the fixed pocket is an open pocketor without a lid, then the one or more processors 202 may be configuredto not create a step for opening a lid. The one or more processors 202may be configured to receive data related to such characteristics ofpockets 130 from the electronic medication storage cabinets 104, and theone or more processors 202 may associate each pocket 130 with itscorresponding characteristics and store the association in a storageunit associated with the electronic medication storage system server108.

In some implementations, the created steps may be a sequence ofgraphical steps configured to instruct a user to fill the pocket in anappropriate manner. In some implementations, the one or more processors202 may associate the created steps with the ordered medication, andstore the association in a storage unit associated with the electronicmedication storage system server 108. The one or more processors 202 maytransmit the association and the created steps to the electronicmedication storage cabinet 104. The one or more processors 202 may beconfigured to cause the display of the created steps associated with anordered medication on a display device, such as display device 312 ofthe electronic medication storage cabinet 104, when the orderedmedication is delivered to the electronic medication storage cabinet104. The method 400 proceeds to block 490. The one or more processors202 schedule the ordered medication for delivery to the electronicmedication storage cabinet 104 (block 490). Additional details ofdelivering an ordered medication to the electronic medication storagecabinet are described herein in with reference to FIGS. 5A and 5B.

Returning to block 430, if the one or more processors 202 determine thata valid fixed pocket is not available (‘NO’ at block 430), then themethod 400 proceeds to block 434. The one or more processors 202determine whether contents of a fixed pocket can be combined withcontents of another fixed pocket (block 434). The one or more processors202 may be configured to determine that contents of a first fixed pocketcan be combined with contents of another fixed pocket if a uniqueidentifier of the medication in the first fixed pocket is the same as aunique identifier of the medication in another fixed pocket. Asdescribed above, in some implementations, the one or more processors 202may be configured to determine the unique identifier of a medicationbased on received data related to the medications from the medicationsystems 110 and/or electronic medication storage cabinet 104. The one ormore processors 202 may be configured to determine the pockets thatcontain medications with the same identifiers based on data related to amedication and a pocket 130 in which it is placed in an electronicmedication storage cabinet 104.

If the one or more processors 202 determine that contents of a fixedpocket can be combined with contents of another fixed pocket (‘YES’ atblock 434), then the method proceeds to block 435. The one or moreprocessors 202 creates steps to instruct the user to dispense theordered medication in a baggie (block 435). The one or more processors202 creates steps to combine the contents from one fixed pocket withcontents from another fixed pocket (block 436). The one or moreprocessors 202 may be configured to create steps to combine inventory.In some implementations, the created steps may be a sequence ofgraphical steps configured to instruct a user to remove contents from afirst pocket and store contents in a second pocket. In someimplementations, the one or more processors 202 associate the freedfixed-pocket to the ordered medication. The one or more processors 202create steps to fill the freed or empty fixed-pocket (block 437). Themethod 400 proceeds to block 490. The one or more processors 202schedule the ordered medication for delivery to the electronicmedication storage cabinet 104 (block 490).

At block 434, if the one or more processors 202 determine that thecontents of a fixed-pocket cannot be combined with contents of anotherfixed-pocket (NO′ at block 434), then the method 400 proceeds to block438. The one or more processors 202 determine whether any of the currentinventory in any fixed-pocket of the electronic medication storagecabinet 104 can be removed (block 438). As described above, the methodproceeds to block 439 to determine whether current inventory may beremoved from pockets of the electronic medication storage cabinet 104.If the one or more processors 202 determine that the current inventorycannot be removed (‘NO’ at block 438), then the one or more processors202 determine and store an indicator in a storage unit (e.g., a flag ina register of a storage unit), which represents that for the orderedmedication space in fixed pockets of an electronic medication storagecabinet 104 is not available. The method 400 proceeds to the block 403,and at block 403, the one or more processors 202 may be configured todetermine if space in fixed pockets is available for this orderedmedication based on the stored indicator. If the one or more processors202 determines that the space in fixed pockets is not available for theordered medication, then the method 400 proceeds to block 470. The oneor more processors 202 determine that the ordered medication can bepackaged and labeled for uncontrolled storage (block 470). The one ormore processors 202 may transmit a message to the medication system 110indicating that the ordered medication can be packaged and labelled foruncontrolled storage.

Returning to block 438, if the one or more processors 202 determine thatthe current inventory can be removed (‘YES’ at block 438), then themethod 400 proceeds to block 439. The one or more processors 302 createsteps to instruct the user to dispense the ordered medication in abaggie (block 439). The one or more processors 302 create steps toremove contents from a fixed-pocket (block 440). The one or moreprocessors 302 create steps to fill the freed or empty pocket (block441). The one or more processors 302 may associate the freed pocket withthe ordered medication. The method 400 proceeds to block 490. The one ormore processors 202 schedule the ordered medication for delivery to theelectronic medication storage cabinet 104 (block 490).

Returning to block 408, if the one or more processors 202 determine thatthe ordered medication is a patient-specific medication, then the method400 proceeds to block 442, as shown in FIG. 4C. The one or moreprocessors 202 determines whether the ordered medication is a controlledsubstance (block 442). In some implementations, the one or moreprocessors 202 may determine if the ordered medication is a controlledsubstance based on a stored set of rules that specify a list ofmedications that are predetermined to be controlled substances. If theone or more processors 202 determine that the ordered medication is acontrolled substance (‘YES’ at block 442), then the method proceeds toblock 443. The one or more processors 202 determine whether theelectronic medication storage cabinet 104 supports dynamic pockets(block 443). If the one or more processors 202 determine that theelectronic medication storage cabinet 104 supports dynamic pockets(‘YES’ at block 443), then the method proceeds to block 444. The one ormore processors 202 initiate the process of checking for available spacein the dynamic pockets of the electronic medication storage cabinet 104(block 444), and the method 400 proceeds to block 410.

If the one or more processors 202 determine that the electronicmedication storage cabinet 104 does not support dynamic pockets (‘NO’ atblock 443), then the method 400 proceeds to block 445. The one or moreprocessors 202 determine whether the electronic medication storagecabinet 104 supports fixed-pockets (block 445). If the one or moreprocessors 202 determine that the electronic medication storage cabinet104 supports fixed-pockets (‘YES’ at block 445), then the method 400proceeds to block 446. The one or more processors 202 initiate theprocess of checking for available space in fixed-pockets of theelectronic medication storage cabinet 104 (block 446), and the method400 proceeds to block 430. If the one or more processors 202 determinethat the electronic medication storage cabinet 104 does not supportfixed pockets, then the method 400 proceeds to block 403. In someimplementations, if the one or more processors 202 determine that theelectronic medication storage cabinet 104 does not support fixedpockets, then the one or more processors 202 determine and store anindicator in a storage unit (e.g., a flag in a register of a storageunit), which represents that space is unavailable in the pockets of theelectronic medication storage cabinet 104. The method 400 proceeds tothe block 403, and at block 403, the one or more processors 202 may beconfigured to determine if space in the pockets is available for theordered medication based on the stored indicator. If the one or moreprocessors 202 determines that the space in the pockets is unavailablefor the ordered medication, then the method 400 proceeds to block 470.

At block 442, if the one or more processors 202 determine that orderedmedication is not a controlled substance, then the method 400 proceedsto block 447. The one or more processors 202 determine whether thepatient is associated with a particular pocket (block 447). As describedabove, the electronic medication storage system server 108 may receivedata related to patients and pockets 130 of electronic medicationstorage cabinets 104, including associations between patients and one ormore pockets 130 in an electronic medication storage cabinet 104. Basedon the received data, the one or more processors 202 may determinewhether the patient is associated with a pocket 130 in the electronicmedication storage cabinet 104. If the one or more processors 202determine that the patient is not associated with a pocket (‘NO’ atblock 447), then the method 400 proceeds to block 409. If the one ormore processors 202 determine that the patient is associated with apocket (‘YES’ at block 447), then the method 400 proceeds to block 448.The one or more processors 202 determine whether sufficient space isavailable in the associated pocket (block 448). If the one or moreprocessors 202 determine that sufficient space is not available in theassociated pocket (‘NO’ at block 448), then the method 400 proceeds toblock 409. If the one or more processors 202 determine that sufficientspace is available in the associated pocket (‘YES’ at block 448), thenthe one or more processors 202 determine that the medication can beplaced in the pocket 130 associated with the patient. The method 400proceeds to block 490. The one or more processors 202 schedule theordered medication for delivery to the electronic medication storagecabinet 104 (block 490).

Turning now to FIGS. 5A-5B, there are shown flowcharts illustrating anoptimized process of loading a medication in an electronic medicationstorage cabinet. For the purpose of illustrating a clear example,components of the network architecture 100, shown and described withreference to FIG. 1, components of the electronic medication storagesystem server 108, shown and described with reference to FIG. 2, andcomponents of the electronic medication storage cabinet 104, shown anddescribed with reference to FIG. 3, and processes described withreference to FIGS. 4A-4D may be used to describe the optimized processof loading a medication in an electronic medication storage cabinet.

The method 500 includes receiving, by one or more processors 302 of theelectronic medication storage cabinet 104 (e.g., electronic medicationstorage cabinet 104-1), a user login information (block 501). The one ormore processors 302 may be configured to determine whether the user isauthorized user. The one or more processors 302 cause a prompt to bedisplayed on a display device (e.g., display device 312) associated withthe electronic medication storage cabinet 104 for scan of an orderedmedication (block 502). The one or more processors 302 receiveinformation of the scanned medication (block 503). Based on the receivedinformation of the scanned medication, the one or more processors 302determine whether the scanned medication can be placed in a dynamicpocket in the electronic medication storage cabinet 104 (block 504). Theone or more processors 302 determine whether the scanned medication willbe stored in a dynamic pocket based on information generated for thescanned medication based on the processes described with reference toFIGS. 4A-4D.

If the one or more processors 302 determine that the scanned medicationwill be loaded into a dynamic pocket (‘YES’ at block 504), then themethod 500 proceeds to block 505. The one or more processors 302 causethe electronic medication storage cabinet 104 to open a movable drawer120 in which the unassigned dynamic pocket containing the scannedmedication will be placed (block 505). The one or more processors 302may be configured to select a drawer 120 based on the steps created bythe electronic medication storage system server 108 for the scannedmedication based on the processes described with reference to FIGS.4A-4D.

The one or more processors 302 determine if loading the scannedmedication in the electronic medication storage cabinet 104 requiresreorganization of one or more dynamic pockets of the electronicmedication storage cabinet 104 (block 506). Based on the steps createdby the electronic medication storage system server 108, the one or moreprocessors 302 determine whether the reorganization of the one or moredynamic pockets is required. For example, if the electronic medicationstorage cabinet 104 has not received any data related to steps createdfor reorganizing one or more dynamic pockets, then the one or moreprocessors 302 determine that reorganization of dynamic pockets are notrequired for loading the scanned medication in the electronic medicationstorage cabinet 104.

If the one or more processors 302 determine that loading the scannedmedication in the electronic medication storage cabinet 104 requiresreorganization of one or more dynamic pockets 130 (‘YES’ at block 506),then the method 500 proceeds to block 507. The one or more processors302 provide the created steps to reorganize one or more dynamic pocketsfor display (block 507). The one or more processors 302 may provide thecreated steps for display on a display device associated with theelectronic medication storage cabinet 104. The one or more processors302 may provide the created steps in a sequence for display. For each ofthe created steps, the one or more processors 302 may be configured todetermine whether the step is successfully completed. Additional detailsof determining whether the created steps are successfully completed aredescribed below with reference to FIG. 6. The method proceeds to block508.

If the one or more processors 302 determine that loading the scannedmedication in the electronic medication storage cabinet 104 does notrequire reorganization of one or more dynamic pockets 130 (‘NO’ at block506), then the method 500 proceeds to block 508. The one or moreprocessors 302 determine whether loading the scanned medication in theelectronic medication storage cabinet 104 require combining contents ofone or more dynamic pockets (block 508). The one or more processors 302may be configured to determine whether combining contents of one or moredynamic pockets with another pocket is required based on the set ofcreated steps received for the scanned medication. If the received setof created steps do not indicate combining contents of dynamic pocketswith other pockets, then the one or more processors 302 determine thatcombining contents of one or more dynamic pockets is not required forloading the scanned medication in the electronic medication storagecabinet 104. Similarly if the received set of created steps indicatecombining contents of one or more dynamic pockets, then the one or moreprocessors 302 determine that combining contents is not necessary forloading the scanned medication in the electronic medication storagecabinet 104.

If the one or more processors 302 determine that combining contents ofone or more dynamic pockets is required for loading the scannedmedication in the electronic medication storage cabinet 104 (‘YES’ atblock 508) to place the unassigned pocket in the electronic medicationstorage cabinet 104, then the method 500 proceeds to block 509. At block509, the one or more processors 302 cause display of the created stepsto combine pockets. The one or more processors 302 cause display ofcreated steps to remove the empty dynamic pocket (block 510). After theone or more processors 302 determine that the steps for combiningpockets and removing empty pockets are successfully completed, themethod 500 proceeds to block 511. The one or more processors 302determines whether loading of the scanned medication require removal ofany medications in the electronic medication storage cabinet 104 (block511). If the one or more processors 302 determine that removal ofmedications is needed to load the scanned drug (‘YES’ at block 511),then the method 500 proceeds to block 512.

The one or more processors 302 cause display of created steps to removecontents from dynamic pockets of the electronic medication storagecabinet 104 (block 512), and the method 500 proceeds to block 513. Theone or more processors 302 causes display of created steps to place thedynamic pocket in the electronic medication storage cabinet 104. Themethod 500 proceeds to block 514. At block 514, the one or moreprocessors 302 determine whether there are any more medications to bedelivered to the electronic medication storage cabinet 104. If the oneor more processors 302 determine that there are additional medicationsto be delivered to the electronic medication storage cabinet 104 (‘YES’at block 514-a), then the method 500 proceeds to block 502. If the oneor more processors 302 determine that there are no additionalmedications to be delivered (‘NO’ at block 514-b), then the method 500proceeds to block 514-b. The one or more processors 302 determinewhether further optimization of the electronic storage cabinet 104 isdesired (block 514-b). The one or more processors 302 may be configuredto receive an input from a user of the electronic storage cabinet 104indicating whether the user desires further optimization of theelectronic storage cabinet 104. Based on the user input, if the one ormore processors 302 determine that the further optimization is desired(‘YES’ at block 514-b), then the method 500 proceeds to block 525. Basedon the user input, if the one or more processors 302 determine thatfurther optimization is not desired (NO′ at block 514-b), then themethod 500 ends.

In some implementations, the one or more processors 302 may beconfigured to transmit a message to electronic storage server system 108in response to determining that further optimization is desired, and theone or more processors 202 may be configured to determine furtheroptimizations based on the process described with reference to FIG. 4D.In some implementations, the one or more processors 302 may beconfigured to determine optimizations of the electronic storage cabinet104 based on the process described above in FIG. 4D.

At block 525, the one or more processors 302 determine whether any ofthe pockets of the electronic storage cabinet 104 include any expiredmedications. As described above, the one or more processors 302 may beconfigured to determine the contents of each pocket, and in someimplementations, based on the contents, the one or more processors 302may be configured to determine whether medication in a pocket hasexpired. If the one or more processors 302 determine that medications inpockets have not expired (‘NO’ at block 525), then the method 500proceeds to block 527. If the one or more processors 302 determine thatmedication in a pocket has expired (‘YES’ at block 525), then the method500 proceeds to block 526. The one or more processors 302 provide, fordisplay, steps generated for removal of the expired items (block 526).After the one or more processors 302 determine that the steps generatedfor removal of the expired items are successfully completed, the method500 proceeds to block 527.

The one or more processors 302 determine whether other contents ofpockets can be removed (block 527). In some implementations, the one ormore processors 302 may be configured to determine whether contents of apocket will be removed based on determining whether any of the pocketshave medications for discharged patients. Additional details of removingmedications of discharged patients are described above with reference toFIG. 4D. If the one or more processors 302 determine that other contentsof pockets do not have to be removed (‘NO’ at block 527), then themethod proceeds to block 531. If the one or more processors 302determine that other contents of pockets can be combined (‘YES’ at block527), then the method 500 proceeds to block 528. The one or moreprocessors 302 determine a type of the pocket from which contents can beremoved (block 528).

If the one or more processors 302 determine that the pocket is a dynamicpocket (‘Dynamic Pocket’ at block 528), then the method 500 proceeds toblock 529. The one or more processors 302 provide for display stepsgenerated to remove the dynamic pocket (block 529). After the one ormore processors 302 determine that the steps for removing the dynamicpockets were successfully completed, then the method 500 proceeds toblock 531. If the one or more processors 302 determine that the pocketis a fixed pocket (‘Fixed Pocket’ at block 528), then the method 500proceeds to block 530. The one or more processors 302 provide fordisplay steps generated to remove contents from the fixed pocket (block529) After the one or more processors 302 determine that the steps forremoving the contents from the fixed pocket were successfully completed,then the method 500 proceeds to block 531.

The one or more processors 302 determine whether contents of any pocketsmay be combined (block 531). The one or more processors 302 may beconfigured to combine medications of one pocket with another pocket ifthe medications in the two pockets have the same unique identifier. Ifthe one or more processors 302 determine that the contents of thepockets may not be combined (‘NO’ at block 531), then the method 500ends. If the one or more processors 302 determine that the contents ofpockets may be combined (‘YES’ at block 531), then the method 500proceeds to block 532. The one or more processors 302 provide fordisplay steps generated for combining contents of one pocket withanother pocket (block 532). The one or more processors 302 determine atype of the pocket (block 533).

If the one or more processors 302 determine that the type of the pocketis a fixed pocket (‘Fixed Pockets’ at block 533), then the method 500proceeds to block 534. The one or more processors 302 provide fordisplay steps generated to unload freed pocket (block 534). After theone or more processors 302 confirm that the steps are successfullycompleted, the method 500 proceeds block 531. If the one or moreprocessors 302 determine that the type of the pocket is dynamic pocket(‘Dynamic Pockets’ at block 534), then the method 500 proceeds to block535. The one or more processors 302 provide for display steps generatedto remove the freed dynamic pocket. After the one or more processors 302confirm that the steps are successfully completed, the method 500proceeds block 531. At block 531, when the one or more processors 302determine that no pockets can be combined (‘NO’ at block 531), then themethod 500 ends.

Returning block 504, if the one or more processors 302 determine scannedmedication will not be stored in the dynamic pocket (NO′ at block 504),then the method 500 proceeds to block 515. The one or more processors302 determine whether the scanned medication should be refrigerated(block 515). If the one or more processors determine that the scannedmedication should be refrigerated (‘YES’ at block 515), then the method500 proceeds to block 516. The one or more processors 302 cause displayof a prompt to place the scanned medication in the refrigerator. If theone or more processors 302 determine that the scanned medication shouldnot be refrigerated (NO′ at block 515), then the method proceeds toblock 517. The one or more processors 302 determine whether the scannedmedication should be placed in a tower (block 517). If the one or moreprocessors 302 determine that the scanned medication should be placed inthe tower (‘YES’ at block 517), then the method 500 proceeds to block518. The one or more processors 302 cause the display of a prompt to auser to place the scanned medication in the tower (block 518).

If the one or more processors 302 determine that the scanned medicationshould not be placed in tower (‘NO’ at block 517), then the method 500proceeds to block 519. The one or more processors 302 cause a drawer ofthe electronic medication storage cabinet 104 to be opened. The openeddrawer may include one or more fixed pockets. The method 500 proceeds toblock 520, and at block 520, the one or more processors 302 determinewhether loading of the scanned medication will require contents of anyfixed pocket to be combined with contents of another fixed pocket. Ifthe one or more processors 302 determine that the contents will need tobe combined (‘YES’ at block 520), then the method proceeds to block 521.The one or more processors 302 cause display of the created steps tocombine contents of one fixed pocket with contents of another fixedpocket (block 521). The method 500 proceeds to block 522. At block 520,if the one or more processors 302 determine that the contents of onefixed pocket are not required to be combined with contents of anotherfixed pocket (NO at block 520), then the method proceeds to block 522.

The one or more processors 302 determines whether removal of anycontents of any fixed pockets is required for loading scanned medication(block 522). If the one or more processors 302 determine that removal isneeded (‘YES’ at block 522), then the method proceeds to block 523. Theone or more processors 302 causes display of the created steps to removecontents of a fixed pocket (block 523), and the method proceeds to block524. If the one or more processors 302 determine that removal is notneeded (‘NO’ at block 522), then the method proceeds to block 524. Atblock 524, the one or more processors 302 cause display of the createdsteps to place the scanned medication into the freed or empty pocket.The method continues to block 514.

In some implementations, the one or more processors 302 determinewhether a step of the created steps is successfully completed. In someimplementations, the one or more processors 302 may be configured todetermine that a current step of the created steps is successfullycompleted based on data from one or more sensors of the electronicmedication storage cabinet. For example, if the current step requiresplacing a pocket 130 in a certain location of the drawer 120 of theelectronic medication storage cabinet 104, the processor 302 may beconfigured to determine whether pocket was placed in the correctlocation based on the data from sensors associated with that locationthat indicate that the pocket was placed in that location.

In some implementations, if the processor 302 determines that a currentstep is not successfully completed then the one or more processors 302may be configured to generate a remedial step. The one or moreprocessors 302 may be configured to generate the remedial step based onuser inputs. For example, if the one or more processors 302, via the oneor more sensor devices, determine that the pocket is placed in alocation different from the expected location, then the processor 302may be configured to generate a remedial step that corrects the error byproviding instructions to remove the pocket from that location. The oneor more processors 302 may cause the remedial step to be displayed. Theone or more processors 302 may determine whether the remedial step issuccessfully completed. For example, the one or more processors 302 maybe configured to determine that the remedial step of removing the pocketfrom the wrong location is successfully completed based on data fromsensors associated with that location.

Although some of various drawings illustrate a number of logical stagesin a particular order, stages that are not order dependent may bereordered and other stages may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beobvious to those of ordinary skill in the art, so the ordering andgroupings presented herein are not an exhaustive list of alternatives.Moreover, it should be recognized that the stages could be implementedin hardware, firmware, software, or any combination thereof.

Illustration of Subject Technology as Clauses

Various examples of aspects of the disclosure are described as numberedclauses (1, 2, 3, etc.) for convenience. These are provided as examples,and do not limit the subject technology. Identifications of the figuresand reference numbers are provided below merely as examples and forillustrative purposes, and the clauses are not limited by thoseidentifications.

Clause 1. A method, comprising: providing an electronic medicationstorage cabinet comprising a plurality of drawers, each drawerconfigured with a plurality of storage pockets, the drawer configuredwith a plurality of sensors arranged to identify a positioning of theplurality of storage pockets within the drawer; receiving an indicationof a new medicine container to be loaded in the electronic medicationstorage cabinet; displaying a first step of a sequence of one or moresteps to load the medicine container into an electronic medicationstorage cabinet on a display on the electronic medication storagecabinet, wherein the sequence is generated based on a mapping algorithm;determining whether the first step of the sequence of the one or moresteps is associated with one of the plurality of drawers; in response todetermining that the first step is associated with one of the pluralityof drawers, automatically unlocking the associated drawer; determiningwhether the first step is successfully completed; in response todetermining that the first step is successfully completed, determiningwhether execution of any additional steps is pending; and generating analert in response to determining that execution of no additional stepsis pending.

Clause 2. The method of Clause 1, further comprising: providing, on thedisplay, a first prompt to remove a first storage pocket from a firstlocation within the plurality of drawers, wherein first prompt isassociated with the first step; verifying, via the plurality of sensors,that the first storage pocket is removed; and in response to verifyingthat the first storage pocket is removed, determining that the firststep is successfully completed.

Clause 3. The method of Clause 2, further comprising: in response todetermining that execution of at least one additional step is pending,transitioning to a next pending step in the sequence of the one or moresteps; providing, on the display, a second prompt to relocate the firststorage pocket within a first available space within the plurality ofdrawers, wherein the second prompt is associated with the next pendingstep; and verifying, via the plurality of sensors, that the firststorage pocket was relocated to the first available space.

Clause 4. The method of Clause 3, further comprising: in response toverifying that the first storage pocket was relocated to the firstavailable space, determining that the next pending step is successfullycompleted; transitioning to a subsequent pending step in the sequence ofthe one or more steps; and providing, on the display, a third prompt toinsert a new storage pocket within a second available space within theplurality of drawers, wherein the third prompt is associated with thesubsequent pending step.

Clause 5. The method of Clause 1, further comprising: in response todetermining that the first step is not successfully completed,generating a remedial step; and displaying the remedial step on thedisplay.

Clause 6. The method of Clause 5, further comprising: determiningwhether the remedial step is successfully completed; and in response tothe remedial step being successfully completed, displaying the firststep of the sequence of the one or more steps on the display.

Clause 7. The method of Clause 1, further comprising: prior toautomatically unlocking the associated drawer, requesting authorizedcredentials to access the electronic medication storage cabinet; andreceiving an indication authorizing access to the electronic medicationstorage cabinet.

Clause 8. The method of Clause 1, wherein the plurality of sensors arearranged in a grid pattern in the drawer.

Clause 9. The method of Clause 1, wherein one or more of the pluralityof sensors are arranged in a perimeter around the inside of the drawer.

Clause 10. The method of Clause 1, wherein the alert is a visual alert.

Clause 11. A method, comprising: providing a electronic medicationstorage cabinet comprising a plurality of drawers, each drawerconfigured with a plurality of removable storage pockets, the drawerconfigured with a plurality of sensors arranged to identify apositioning of the plurality of removable storage pockets within thedrawer; receiving an indication of a new medicine container to be storedin the electronic medication storage cabinet requires a new storagepocket to be added to the electronic medication storage cabinet;determining, based on receiving the indication, that at least a subsetof removable storage pockets within one or more of the plurality ofdrawers require repositioning to accommodate the new pocket; generating,based on a mapping algorithm, a new arrangement of the subset ofremovable storage pockets and the new pocket within the one or more ofthe plurality of drawers; executing, at the electronic medicationstorage cabinet, a predetermined sequence of steps for effecting the newarrangement, comprising: automatically unlocking a first drawer of theplurality of drawers; providing a first prompt to remove at least afirst storage pocket of the subset of removable storage pockets;verifying, via the plurality of sensors, that the first storage pocketwas removed; providing a second prompt to relocate the first pocketwithin a first available space within the one or more of the pluralityof drawers; verifying, via the plurality of sensors, that the firstpocket was relocated; providing a third prompt to insert the new pocketwithin a second available space of the one or more of the plurality ofdrawers; verifying, via the plurality of sensors, that the new pocketwas inserted.

Clause 12. The method of Clause 11, wherein, prior to providing thethird prompt, the executing further comprises: automatically unlocking asecond drawer of the plurality of drawers; providing a fourth prompt toremove at least a second storage pocket of the subset of removablestorage pockets; verifying, via the plurality of sensors, that thesecond storage pocket was removed; providing a fifth prompt to relocatethe second pocket into a second available space within the one or moreof the plurality of drawers; verifying, via the plurality of sensors,that the second pocket was relocated.

Clause 13. The method of Clause 11, wherein, prior to automaticallyunlocking the first drawer; requesting access authorizationverification; and receiving an indication authorizing access to theelectronic medication storage cabinet.

Clause 14. The method of Clause 11, wherein, prior to automaticallyunlocking the first drawer; requesting access authorizationverification; receiving an indication of limited access to theelectronic medication storage cabinet; and generating, based on themapping algorithm and the received indication of limited access, asecond arrangement of the subset of removable storage pockets.

Clause 15. The method of Clause 14, further comprising: executing, atthe electronic medication storage cabinet, a second predeterminedsequence of steps for effecting the second arrangement, comprising:automatically unlocking a second drawer of the plurality of drawers;providing a fourth prompt to remove at least a second storage pocket ofthe subset of removable storage pockets; verifying, via the plurality ofsensors, that the second storage pocket was removed; providing a fifthprompt to relocate the second pocket within a second available spacewithin the one or more plurality of drawers; verifying, via theplurality of sensors, that the second pocket was relocated; providing athird prompt to insert the new pocket within the one or more of theplurality of drawers; verifying, via the plurality of sensors, that newfirst pocket was inserted.

Clause 16. A system, comprising: a memory storing instructions; and oneor more processors coupled with the memory and configured to execute theinstructions to cause the system to perform the steps of the method inclaim 1.

Further Consideration

In some embodiments, any of the clauses herein may depend from any oneof the independent clauses or any one of the dependent clauses. In oneaspect, any of the clauses (e.g., dependent or independent clauses) maybe combined with any other one or more clauses (e.g., dependent orindependent clauses). In one aspect, a claim may include some or all ofthe words (e.g., steps, operations, means or components) recited in aclause, a sentence, a phrase or a paragraph. In one aspect, a claim mayinclude some or all of the words recited in one or more clauses,sentences, phrases or paragraphs. In one aspect, some of the words ineach of the clauses, sentences, phrases or paragraphs may be removed. Inone aspect, additional words or elements may be added to a clause, asentence, a phrase or a paragraph. In one aspect, the subject technologymay be implemented without utilizing some of the components, elements,functions or operations described herein. In one aspect, the subjecttechnology may be implemented utilizing additional components, elements,functions or operations.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the claims to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The implementations were chosen in order to best explain theprinciples underlying the claims and their practical applications, tothereby enable others skilled in the art to best use the implementationswith various modifications as are suited to the particular usescontemplated.

There may be many other ways to implement the subject technology.Various functions and elements described herein may be partitioneddifferently from those shown without departing from the scope of thesubject technology. Various modifications to these configurations willbe readily apparent to those skilled in the art, and generic principlesdefined herein may be applied to other configurations. Thus, manychanges and modifications may be made to the subject technology, by onehaving ordinary skill in the art, without departing from the scope ofthe subject technology.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list (i.e.,each item). The phrase “at least one of” does not require selection ofat least one of each item listed; rather, the phrase allows a meaningthat includes at least one of any one of the items, and/or at least oneof any combination of the items, and/or at least one of each of theitems. By way of example, the phrases “at least one of A, B, and C” or“at least one of A, B, or C” each refer to only A, only B, or only C;any combination of A, B, and C; and/or at least one of each of A, B, andC.

Furthermore, to the extent that the term “include,” “have,” or the likeis used in the description or the claims, such term is intended to beinclusive in a manner similar to the term “comprise” as “comprise” isinterpreted when employed as a transitional word in a claim. The word“exemplary” is used herein to mean “serving as an example, instance, orillustration.” Any embodiments described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otherembodiments.

In one or more aspects, the terms “about,” “substantially,” and“approximately” may provide an industry-accepted tolerance for theircorresponding terms and/or relativity between items.

A reference to an element in the singular is not intended to mean “oneand only one” unless specifically stated, but rather “one or more.” Theterm “some” refers to one or more. All structural and functionalequivalents to the elements of the various configurations describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and intended to be encompassed by the subject technology.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe above description.

While certain aspects and embodiments of the subject technology havebeen described, these have been presented by way of example only, andare not intended to limit the scope of the subject technology. Indeed,the novel methods and systems described herein may be embodied in avariety of other forms without departing from the spirit thereof. Theaccompanying claims and their equivalents are intended to cover suchforms or modifications as would fall within the scope and spirit of thesubject technology.

What is claimed is:
 1. A method, comprising: providing an electronicmedication storage cabinet comprising a plurality of drawers, eachdrawer comprising a plurality of sensors arranged and configured toidentify a positioning of a plurality of storage pockets within thedrawer; receiving an indication of a new medicine container to be loadedin the electronic medication storage cabinet; generating a sequence ofone or more steps to load the new medicine container into the electronicmedication storage cabinet; displaying, on a display screen associatedwith the electronic medication storage cabinet, a first step of thesequence of one or more steps; determining an association between thefirst step of the sequence of the one or more steps and a respectivedrawer of the plurality of drawers; in response to determining theassociation between the first step and the respective drawer,automatically unlocking the respective drawer; determining whether thefirst step is successfully completed based on signals received from theplurality of sensors of the respective drawer; and in response todetermining that the first step is successfully completed, determiningwhether execution of any additional steps are pending, and indicatingvia the display screen whether any additional steps are pending.
 2. Themethod of claim 1, further comprising: providing, on the display, afirst prompt to remove a first storage pocket from a first locationwithin the plurality of drawers, wherein first prompt is associated withthe first step; verifying, via the plurality of sensors, that the firststorage pocket is removed; and in response to verifying that the firststorage pocket is removed, determining that the first step issuccessfully completed.
 3. The method of claim 2, further comprising: inresponse to determining that execution of at least one additional stepis pending, transitioning to a next pending step in the sequence of theone or more steps; providing, on the display, a second prompt torelocate the first storage pocket within a first available space withinthe plurality of drawers, wherein the second prompt is associated withthe next pending step; and verifying, via the plurality of sensors, thatthe first storage pocket was relocated to the first available space. 4.The method of claim 3, further comprising: in response to verifying thatthe first storage pocket was relocated to the first available space,determining that the next pending step is successfully completed;transitioning to a subsequent pending step in the sequence of the one ormore steps; and providing, on the display, a third prompt to insert anew storage pocket within a second available space within the pluralityof drawers, wherein the third prompt is associated with the subsequentpending step.
 5. The method of claim 1, further comprising: in responseto determining that the first step is not successfully completed,generating a remedial step; and displaying the remedial step on thedisplay.
 6. The method of claim 5, further comprising: determiningwhether the remedial step is successfully completed; and in response tothe remedial step being successfully completed, displaying the firststep of the sequence of the one or more steps on the display.
 7. Themethod of claim 1, further comprising: prior to automatically unlockingthe respective drawer, requesting authorized credentials to access theelectronic medication storage cabinet; and receiving an indicationauthorizing access to the electronic medication storage cabinet.
 8. Themethod of claim 1, wherein the plurality of sensors are arranged in agrid pattern in the drawer.
 9. The method of claim 1, wherein one ormore of the plurality of sensors are arranged in a perimeter around theinside of the drawer.
 10. The method of claim 1, wherein indicating viathe display screen whether any additional steps are pending comprisesproviding a visual alert on the display screen.
 11. A method,comprising: providing an electronic medication storage cabinetcomprising a plurality of drawers, each drawer comprising a plurality ofsensors arranged and configured to identify a positioning of a pluralityof storage pockets within the drawer; receiving, by one or moreprocessors, an indication of a new medicine container to be stored inthe electronic medication storage cabinet; automatically determining, bythe one or more processors, that the new medicine container requires anew storage pocket to be added to the electronic medication storagecabinet; determining, by the one or more processors, based on receivingthe indication and determining that the new medicine container requiresa new storage pocket, that at least a subset of removable storagepockets within one or more of the plurality of drawers requirerepositioning to accommodate the new storage pocket; generating, by theone or more processors, based on a mapping algorithm, a new arrangementof the subset of removable storage pockets and the new storage pocketwithin the one or more of the plurality of drawers; executing, by theone or more processors, a predetermined sequence of steps for effectingthe new arrangement, comprising: automatically unlocking, by the one ormore processors, a first drawer of the plurality of drawers; providing,by the one or more processors, a first prompt to remove at least a firststorage pocket of the subset of removable storage pockets; verifying, bythe one or more processors, via the plurality of sensors, that the firststorage pocket was removed; providing a second prompt to relocate thefirst storage pocket within a first available space within the one ormore of the plurality of drawers; verifying, by the one or moreprocessors, via the plurality of sensors, that the first storage pocketwas relocated; providing, by the one or more processors, a third promptto insert the new storage pocket within a second available space of theone or more of the plurality of drawers; verifying, by the one or moreprocessors, via the plurality of sensors, that the new storage pocketwas inserted within the second available space.
 12. The method of claim11, wherein, prior to providing the third prompt, the executing furthercomprises: automatically unlocking a second drawer of the plurality ofdrawers; providing a fourth prompt to remove at least a second storagepocket of the subset of removable storage pockets; verifying, via theplurality of sensors, that the second storage pocket was removed;providing a fifth prompt to relocate the second storage pocket into asecond available space within the one or more of the plurality ofdrawers; verifying, via the plurality of sensors, that the secondstorage pocket was relocated.
 13. The method of claim 11, wherein, priorto automatically unlocking the first drawer; requesting accessauthorization verification; and receiving an indication authorizingaccess to the electronic medication storage cabinet.
 14. The method ofclaim 11, wherein, prior to automatically unlocking the first drawer;requesting access authorization verification; receiving an indication oflimited access to the electronic medication storage cabinet; andgenerating, based on the mapping algorithm and the received indicationof limited access, a second arrangement of the subset of removablestorage pockets.
 15. The method of claim 14, further comprising:executing, at the electronic medication storage cabinet, a secondpredetermined sequence of steps for effecting the second arrangement,comprising: automatically unlocking a second drawer of the plurality ofdrawers; providing a fourth prompt to remove at least a second storagepocket of the subset of removable storage pockets; verifying, via theplurality of sensors, that the second storage pocket was removed;providing a fifth prompt to relocate the second storage pocket within asecond available space within the plurality of drawers; verifying, viathe plurality of sensors, that the second storage pocket was relocated;providing a third prompt to insert the new storage pocket within the oneor more of the plurality of drawers; verifying, via the plurality ofsensors, that new first pocket was inserted.
 16. A system, comprising: amemory storing instructions; and one or more processors coupled with thememory and configured to execute the instructions to cause the system toperform operations comprising: receiving an indication of a new medicinecontainer to be loaded in an electronic medication storage cabinet, theelectronic medication storage cabinet comprising a plurality of drawers,each drawer comprising a plurality of sensors arranged and configured toidentify a positioning of a plurality of storage pockets within thedrawer; generating a sequence of one or more steps to load the newmedicine container into the electronic medication storage cabinet;displaying, on a display screen associated with the the electronicmedication storage cabinet, a first step of the sequence of one or moresteps; determining an association between the first step of the sequenceof the one or more steps and a respective drawer of the plurality ofdrawers; in response to determining the association between the firststep and the respective drawer, automatically unlocking the respectivedrawer; determining whether the first step is successfully completedbased on signals received from the plurality of sensors of therespective drawer; and in response to determining that the first step issuccessfully completed, determining whether execution of any additionalsteps are pending, and indicating via the display screen whether anyadditional steps are pending.
 17. The system of claim 16, wherein theoperations further comprise: providing, on the display, a first promptto remove a first storage pocket from a first location within theplurality of drawers, wherein first prompt is associated with the firststep; verifying, via the plurality of sensors, that the first storagepocket is removed; and in response to verifying that the first storagepocket is removed, determining that the first step is successfullycompleted.
 18. The system of claim 17, wherein the operations furthercomprise: in response to determining that execution of at least oneadditional step is pending, transitioning to a next pending step in thesequence of the one or more steps; providing, on the display, a secondprompt to relocate the first storage pocket within a first availablespace within the plurality of drawers, wherein the second prompt isassociated with the next pending step; and verifying, via the pluralityof sensors, that the first storage pocket was relocated to the firstavailable space.
 19. The system of claim 18, wherein the operationsfurther comprise: in response to verifying that the first storage pocketwas relocated to the first available space, determining that the nextpending step is successfully completed; transitioning to a subsequentpending step in the sequence of the one or more steps; and providing, onthe display, a third prompt to insert a new storage pocket within asecond available space within the plurality of drawers, wherein thethird prompt is associated with the subsequent pending step.
 20. Thesystem of claim 16, wherein the plurality of sensors are arranged in agrid pattern in the drawer, and wherein the operations further comprise:prior to automatically unlocking the respective drawer, requestingauthorized credentials to access the electronic medication storagecabinet; and receiving an indication authorizing access to theelectronic medication storage cabinet.